JBoss.orgCommunity Documentation
The Mobicents SIP Presence Server is a free and open source implementation of a SIP Presence Server, as defined by the Internet Engineering Task Force (IETF), the Open Mobile Alliance (OMA), the 3rd Generation Partnership Project (3GPP) and the European Telecommunications Standards Institute (ETSI).
The SIP Presence Server is an entity that accepts, stores and distributes SIP presence information, fully supporting OMA Presence SIMPLE Data Extensions V1.2.
The SIP Presence Server is comprised of the following functional elements:
This functional element manages the publication of presence events, which includes the handling of new publications and the refreshing, modification or removal of already-published information.
This element is also responsible for composing all of the different publications for the same resource. This is because the presence resource, which is also called a presentity, can have multiple publications simultaneously, such as some states published by a user agent or device, and some location data published by a Presence Network Agent (on behalf of the presentity).
In some presence networks, it may be of interest to allow resources to have a static presence state stored in the XDM Server. In cases like these, Presence Publication Control may need to interface with the XDM Server to retrieve and subscribe to (learn about changes to) that information, and use it when composing the final presence information document.
This functional element is responsible for subscribing presence content stored in the XDMS, create and manage the related publications in the Presence Publication Contro.
This functional element handles subscriptions to presence events or to the list of subscribers (watchers) for any specific resource. It is responsible for emitting notifications related to those subscriptions.
Presence authorization rules, which define if a subscription is allowed or rejected and, if allowed, define which transformations to the original presence events are needed, are stored on the XDM Server by the user. Presence Subscription Control needs to retrieve and subscribe to that information.
This element is responsible for interfacing with the XDM Server that manages the user's XML presence rules documents. It is responsible for providing the presence rules to the Presence Subscription Control, which are used to authorize the subscriptions it handles.
Several features of the SIP Presence Server are configurable, through XML files or JMX:
Edit the properties in file $JBOSS_HOME/server/<server_profile>/deploy/mobicents-sip-presence/3-beans/configuration/sip-event/publication/META-INF/jboss-beans.xml
.
This configuration part can also be done through JMX, using the org.mobicents.sippresence:name=SipEventPublicationControl MBean. The configuration changes through JMX are not persistent.
Edit the properties in file $JBOSS_HOME/server/<server_profile>/deploy/mobicents-sip-presence/3-beans/configuration/sip-event/subscription/META-INF/jboss-beans.xml
.
This configuration part can also be done through JMX, using the org.mobicents.sippresence:name=SipEventSubscriptionControl MBean. The configuration changes through JMX are not persistent.
Edit the properties in file $JBOSS_HOME/server/<server_profile>/deploy/mobicents-sip-presence/3-beans/configuration/sip-presence/META-INF/jboss-beans.xml
.
This configuration part can also be done through JMX, using the org.mobicents.sippresence:name=SipPresenceServerManagement MBean. The configuration changes through JMX are not persistent.
The Mobicents SIP Presence Server accepts the following content type to be published and subscribed by users:
The content accepted can be easily extended/modified, one just need to add/remove the related XML schema files in the directory $JBOSS_HOME/server/<server_profile>/deploy/mobicents-sip-presence/3-beans/configuration/sip-presence/xsd
.